Business Systems Why is it important to use systems analysis and design methodologies when building a system? Why not just build the system in whatever way seems to be "quick and easy?" What value is provided by using an "engineering" approach?

Using a consistent and sound systems analysis and design methodology when building any system ensures that the foundational structure of the software or entire computing platform meets the specific goals and objectives of the users it is being designed for. Second, using sound systems analysis and design methodologies ensure that the overarching roadmap for the system stays consistent and does not deviate from the original design goals. Third, using a consistent and sound systems analysis and design methodology ensures that as the system user's needs change, the system can change to reflect their requirements. Fifth, having a sound systems analysis and design methodology ensures that the ongoing systems maintenance of the system can be accomplished on a consistent basis. And sixth, a sound systems and design...

Without a sound and consistent methodology to systems analysis and design, none of these benefits are possible. As a result, when a faulty or badly designed systems analysis and design structure is in place a system will often fail or never completely work correctly in the first place.
How might prototyping be used as part of the SDLC?

As the SDLC is focused on translating requirements into completed software that is tested, launched for use then maintained on an ongoing basis, prototyping is critical for designing applications that accurately reflect user needs. As more software development projects move from being focused on traditional waterfall techniques to agile-based development approaches, prototyping becomes even more important. The greater the agility required in a given development effort, the more important prototyping is. When SDLC is combined with prototyping, development programs and plans stay more aligned to customer or user…